Skip to content

Update GitHub Artifact Actions (major)#244

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/major-github-artifact-actions
Open

Update GitHub Artifact Actions (major)#244
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/major-github-artifact-actions

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Feb 18, 2024

This PR contains the following updates:

Package Type Update Change
actions/download-artifact action major v3.0.2v8.0.1
actions/upload-artifact action major v3.2.1v7.0.0

Release Notes

actions/download-artifact (actions/download-artifact)

v8.0.1

Compare Source

What's Changed

Full Changelog: actions/download-artifact@v8...v8.0.1

v8.0.0

Compare Source

v8 - What's new
Direct downloads

To support direct uploads in actions/upload-artifact, the action will no longer attempt to unzip all downloaded files. Instead, the action checks the Content-Type header ahead of unzipping and skips non-zipped files. Callers wishing to download a zipped file as-is can also set the new skip-decompress parameter to false.

Enforced checks (breaking)

A previous release introduced digest checks on the download. If a download hash didn't match the expected hash from the server, the action would log a warning. Callers can now configure the behavior on mismatch with the digest-mismatch parameter. To be secure by default, we are now defaulting the behavior to error which will fail the workflow run.

ESM

To support new versions of the @​actions/* packages, we've upgraded the package to ESM.

What's Changed

Full Changelog: actions/download-artifact@v7...v8.0.0

v7.0.0

Compare Source

v7 - What's new

[!IMPORTANT]
actions/download-artifact@​v7 now runs on Node.js 24 (runs.using: node24) and requires a minimum Actions Runner version of 2.327.1. If you are using self-hosted runners, ensure they are updated before upgrading.

Node.js 24

This release updates the runtime to Node.js 24. v6 had preliminary support for Node 24, however this action was by default still running on Node.js 20. Now this action by default will run on Node.js 24.

What's Changed
New Contributors

Full Changelog: actions/download-artifact@v6.0.0...v7.0.0

v6.0.0

Compare Source

What's Changed

BREAKING CHANGE: this update supports Node v24.x. This is not a breaking change per-se but we're treating it as such.

New Contributors

Full Changelog: actions/download-artifact@v5...v6.0.0

v5.0.0

Compare Source

What's Changed

v5.0.0

🚨 Breaking Change

This release fixes an inconsistency in path behavior for single artifact downloads by ID. If you're downloading single artifacts by ID, the output path may change.

What Changed

Previously, single artifact downloads behaved differently depending on how you specified the artifact:

  • By name: name: my-artifact → extracted to path/ (direct)
  • By ID: artifact-ids: 12345 → extracted to path/my-artifact/ (nested)

Now both methods are consistent:

  • By name: name: my-artifact → extracted to path/ (unchanged)
  • By ID: artifact-ids: 12345 → extracted to path/ (fixed - now direct)
Migration Guide
✅ No Action Needed If:
  • You download artifacts by name
  • You download multiple artifacts by ID
  • You already use merge-multiple: true as a workaround
⚠️ Action Required If:

You download single artifacts by ID and your workflows expect the nested directory structure.

Before v5 (nested structure):

- uses: actions/download-artifact@v4
  with:
    artifact-ids: 12345
    path: dist

### Files were in: dist/my-artifact/

Where my-artifact is the name of the artifact you previously uploaded

To maintain old behavior (if needed):

- uses: actions/download-artifact@v5
  with:
    artifact-ids: 12345
    path: dist/my-artifact  # Explicitly specify the nested path

New Contributors

Full Changelog: actions/download-artifact@v4...v5.0.0

v4.3.0

Compare Source

What's Changed

New Contributors

Full Changelog: actions/download-artifact@v4.2.1...v4.3.0

v4.2.1

Compare Source

What's Changed

Full Changelog: actions/download-artifact@v4.2.0...v4.2.1

v4.2.0

Compare Source

What's Changed

New Contributors

Full Changelog: actions/download-artifact@v4.1.9...v4.2.0

v4.1.9

Compare Source

What's Changed

New Contributors

Full Changelog: actions/download-artifact@v4.1.8...v4.1.9

v4.1.8

Compare Source

What's Changed

Full Changelog: actions/download-artifact@v4.1.7...v4.1.8

v4.1.7

Compare Source

What's Changed

Full Changelog: actions/download-artifact@v4.1.6...v4.1.7

v4.1.6

Compare Source

What's Changed

Full Changelog: actions/download-artifact@v4.1.5...v4.1.6

v4.1.5

Compare Source

What's Changed

  • Update readme with v3/v2/v1 deprecation notice by @​robherley in #​322
  • Update dependencies @actions/core to v1.10.1 and @actions/artifact to v2.1.5

Full Changelog: actions/download-artifact@v4.1.4...v4.1.5

v4.1.4

Compare Source

What's Changed

Full Changelog: actions/download-artifact@v4...v4.1.4

v4.1.3

Compare Source

What's Changed

New Contributors

Full Changelog: actions/download-artifact@v4...v4.1.3

v4.1.2

Compare Source

v4.1.1

Compare Source

  • Fix transient request timeouts #​249
  • Bump @actions/artifacts to latest version

v4.1.0

Compare Source

What's Changed

New Contributors

Full Changelog: actions/download-artifact@v4...v4.1.0

v4.0.0

Compare Source

What's Changed

The release of upload-artifact@​v4 and download-artifact@​v4 are major changes to the backend architecture of Artifacts. They have numerous performance and behavioral improvements.

ℹ️ However, this is a major update that includes breaking changes. Artifacts created with versions v3 and below are not compatible with the v4 actions. Uploads and downloads must use the same major actions versions. There are also key differences from previous versions that may require updates to your workflows.

For more information, please see:

  1. The changelog post.
  2. The README.
  3. The migration documentation.
  4. As well as the underlying npm package, @​actions/artifact documentation.

New Contributors

Full Changelog: actions/download-artifact@v3...v4.0.0

actions/upload-artifact (actions/upload-artifact)

v7.0.0

Compare Source

v7 What's new

Direct Uploads

Adds support for uploading single files directly (unzipped). Callers can set the new archive parameter to false to skip zipping the file during upload. Right now, we only support single files. The action will fail if the glob passed resolves to multiple files. The name parameter is also ignored with this setting. Instead, the name of the artifact will be the name of the uploaded file.

ESM

To support new versions of the @actions/* packages, we've upgraded the package to ESM.

What's Changed

New Contributors

Full Changelog: actions/upload-artifact@v6...v7.0.0

v6.0.0

Compare Source

v5.0.0

Compare Source

v4.6.2

Compare Source

What's Changed

  • Update to use artifact 2.3.2 package & prepare for new upload-artifact release by @​salmanmkc in #​685

New Contributors

Full Changelog: actions/upload-artifact@v4...v4.6.2

v4.6.1

Compare Source

What's Changed

Full Changelog: actions/upload-artifact@v4...v4.6.1

v4.6.0

Compare Source

What's Changed

Full Changelog: actions/upload-artifact@v4...v4.6.0

v4.5.0

Compare Source

What's Changed

New Contributors

Full Changelog: actions/upload-artifact@v4.4.3...v4.5.0

v4.4.3

Compare Source

What's Changed

Full Changelog: actions/upload-artifact@v4.4.2...v4.4.3

v4.4.2

Compare Source

What's Changed

  • Bump @actions/artifact to 2.1.11 by @​robherley in #​627
    • Includes fix for relative symlinks not resolving properly

Full Changelog: actions/upload-artifact@v4.4.1...v4.4.2

v4.4.1

Compare Source

What's Changed

New Contributors

Full Changelog: actions/upload-artifact@v4.4.0...v4.4.1

v4.4.0

Compare Source

Notice: Breaking Changes ⚠️

We will no longer include hidden files and folders by default in the upload-artifact action of this version. This reduces the risk that credentials are accidentally uploaded into artifacts. Customers who need to continue to upload these files can use a new option, include-hidden-files, to continue to do so.

See "Notice of upcoming deprecations and breaking changes in GitHub Actions runners" changelog and this issue for more details.

What's Changed

Full Changelog: actions/upload-artifact@v4.3.6...v4.4.0

v4.3.6

Compare Source

What's Changed

Full Changelog: actions/upload-artifact@v4...v4.3.6

v4.3.5

Compare Source

What's Changed

Full Changelog: actions/upload-artifact@v4.3.4...v4.3.5

v4.3.4

Compare Source

What's Changed

Full Changelog: actions/upload-artifact@v4.3.3...v4.3.4

v4.3.3

Compare Source

What's Changed

Full Changelog: actions/upload-artifact@v4.3.2...v4.3.3

v4.3.2

Compare Source

What's Changed

New Contributors

Full Changelog: actions/upload-artifact@v4.3.1...v4.3.2

v4.3.1

Compare Source

v4.3.0

Compare Source

What's Changed

Full Changelog: actions/upload-artifact@v4...v4.3.0

v4.2.0

Compare Source

What's Changed

Full Changelog: actions/upload-artifact@v4...v4.2.0

v4.1.0

Compare Source

What's Changed

New Contributors

Full Changelog: actions/upload-artifact@v4...v4.1.0

v4.0.0

Compare Source

What's Changed

The release of upload-artifact@​v4 and download-artifact@​v4 are major changes to the backend architecture of Artifacts. They have numerous performance and behavioral improvements.

ℹ️ However, this is a major update that includes breaking changes. Artifacts created with versions v3 and below are not compatible with the v4 actions. Uploads and downloads must use the same major actions versions. There are also key differences from previous versions that may require updates to your workflows.

For more information, please see:

  1. The changelog post.
  2. The README.
  3. The migration documentation.
  4. As well as the underlying npm package, @​actions/artifact documentation.
New Contributors

Full Changelog: actions/upload-artifact@v3...v4.0.0


Configuration

📅 Schedule: Branch creation - "before 2am" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Feb 18, 2024
@renovate renovate bot force-pushed the renovate/major-github-artifact-actions branch from b5e41fa to 0fc27d3 Compare February 18, 2024 04:36
@renovate renovate bot force-pushed the renovate/major-github-artifact-actions branch 3 times, most recently from 959544f to c2173fa Compare March 1, 2024 19:43
@renovate renovate bot force-pushed the renovate/major-github-artifact-actions branch 3 times, most recently from f09e5d8 to 11bff3e Compare April 24, 2024 17:46
@renovate renovate bot force-pushed the renovate/major-github-artifact-actions branch from 11bff3e to 82c1f3b Compare May 17, 2024 05:11
@renovate renovate bot force-pushed the renovate/major-github-artifact-actions branch 2 times, most recently from 634131d to d5b19b8 Compare July 8, 2024 15:09
@renovate renovate bot force-pushed the renovate/major-github-artifact-actions branch from d5b19b8 to 8eef99b Compare July 17, 2024 03:32
@renovate renovate bot force-pushed the renovate/major-github-artifact-actions branch 3 times, most recently from 8ca40fa to d810f7c Compare August 6, 2024 17:01
@renovate renovate bot force-pushed the renovate/major-github-artifact-actions branch 3 times, most recently from bac28ce to 318de6c Compare August 29, 2024 14:33
@renovate renovate bot force-pushed the renovate/major-github-artifact-actions branch from 318de6c to 8bc9e00 Compare August 30, 2024 23:00
@renovate renovate bot force-pushed the renovate/major-github-artifact-actions branch 2 times, most recently from 6eb84cd to 380baa3 Compare September 27, 2024 04:46
@renovate renovate bot force-pushed the renovate/major-github-artifact-actions branch 3 times, most recently from db26b1d to 2658688 Compare October 9, 2024 18:44
@renovate renovate bot force-pushed the renovate/major-github-artifact-actions branch from 2658688 to 40e45ac Compare October 29, 2024 00:40
@renovate renovate bot force-pushed the renovate/major-github-artifact-actions branch from 40e45ac to 12b6f43 Compare December 17, 2024 22:24
@renovate renovate bot force-pushed the renovate/major-github-artifact-actions branch from 12b6f43 to 6b11934 Compare January 10, 2025 18:56
@renovate renovate bot force-pushed the renovate/major-github-artifact-actions branch 2 times, most recently from a869ffa to ff2fa8d Compare February 25, 2025 22:27
@renovate renovate bot force-pushed the renovate/major-github-artifact-actions branch from ff2fa8d to fd8e188 Compare March 18, 2025 16:40
@renovate renovate bot force-pushed the renovate/major-github-artifact-actions branch from fd8e188 to c613cb6 Compare March 19, 2025 19:57
@renovate renovate bot force-pushed the renovate/major-github-artifact-actions branch from c613cb6 to 330b077 Compare April 24, 2025 19:32
@renovate renovate bot force-pushed the renovate/major-github-artifact-actions branch from 330b077 to 1ec8025 Compare August 7, 2025 11:04
@renovate renovate bot changed the title Update GitHub Artifact Actions to v4 (major) Update GitHub Artifact Actions (major) Aug 7, 2025
@renovate renovate bot force-pushed the renovate/major-github-artifact-actions branch from 1ec8025 to 8da7b21 Compare October 24, 2025 22:59
@renovate renovate bot force-pushed the renovate/major-github-artifact-actions branch from 8da7b21 to 34abc97 Compare December 12, 2025 21:48
@renovate renovate bot force-pushed the renovate/major-github-artifact-actions branch from 34abc97 to 820e918 Compare February 26, 2026 20:37
@renovate renovate bot force-pushed the renovate/major-github-artifact-actions branch from 820e918 to 756b6d3 Compare March 11, 2026 17:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants